General Information Information on the transmitted data. Business unit Location of a branch office. Place/ Location code UN/Locode; e.g. the location of the user's branch office. Location name. If there is no UN/LoCode available for this place, alternatively the name can be set. Communication information. Contains information on sender, recipients and creation time. Communication participants Up to 11 entries can be sent: SENDER - mandatory with DAKOSY-code EDI_PROVIDER - optional; 'DAKOSY', if message should be processed by DAKOSY RECIPIENT - mandatory with DAKOSY-Code. Maximum of nine entries is possible. Date and time of message creation. container number Format: bytes content 1 - 4 Prefix 5 - 12 Number corresponds to AC02 field number 714/715 container length length of the container in feet according to HABIS code directory A18 corresponds to AC02 field number 711 container height height of the container according to HABIS code directory A19 corresponds to AC02 field number 712 container type according to HABIS code directory A05 corresponds to AC02 field number 713 wagon number number of the rail road wagon the container has been loaded onto quay code of the quay operator answering the status query corresponds to AC02 field number 710 ocean carrier code of the ocean carrier according to DAKOSY key directory ocean carrier / customer code corresponds to AC02 field number 716 type type of deletion T = transport order C = container Position Position of the container (as transmitted by the customer in the transport order container segment Only if type = C The element is not allowed when communicating with ACTION, UNIKAT or TRAFIC. dispatcher name of the dispatcher who accepted the transport order telephone number of the dispatcher fax number of the dispatcher dispatch attribute according to DAKOSY key directory error / status code transaction TR02 If the dispacth attribute is >500 or 401, 420, 421 and 422 it is an indication for a serious error, that should be resolved before the transport. corresponds to AC02 field number 717 dispatch area corresponds to AC02 field number 718 block block of the depot area the container is stored corresponds to AC02 field number 719 row row within the block of the depot area the container is stored corresponds to AC02 field number 720 position place/position of the container within the row fo the depot area corresponds to AC02 field number 721 level place/position of the container within the row fo the depot area corresponds to AC02 field number 722 general EDI-error code code assigned according to the key directory in the appendix or the data field number of the data field containing the error corresponds to AC02 field number 901 error type A = automatic rejection M = manual rejection initiator initiator of the error message short text explanatory short text regarding the error code/ error message. In the case of incorrect line structure, the line number can also be given. corresponds to AC02 field number 902 text1 explanatory text regarding the error message corresponds to AC02 field number 910/911/912/913 incorrect content transmission of the incorrect data field content corresponds to AC02 field number 914 HABIS order number only transport mode = R corresponds to AC02 field number 701 HABIS customer status code HABIS customer status value of the customer status filed in the HABIS classic production system corresponds to AC02 field number 702 HABIS customs status code HABIS customs status value of the customs status filed in the HABIS classic production system corresponds to AC02 field number 703 HABIS sales status code HABIS sales status value of the sales status filed in the HABIS classic production system corresponds to AC02 field number 704 HABIS production status code HABIS production status value of the production status filed in the HABIS classic production system corresponds to AC02 field number 705 HABIS quay status code HABIS quay status value of the quay status filed in the HABIS classic production system corresponds to AC02 field number 706 General Message definition Describes the contents of a message (metainfo and data) User information Information on the user who sent the message. Metainfo Contains information concerning transaction type, communication parties etc. Transaction type Specifies the transaction type (GM01, AB01 etc.). Only one transaction per file is allowed. Different types must be sent in separate files. Application name Name of the application served by the interface. E.g. SEEDOS, ATLAS Testflag 0 - false (default); 1- true; transmission for test purpose Number of messages Number of messages (elements) that are collected in the transmitted file. reference reference of the transport order within the ACTION / UNKAT systems number of positions number of positions (containers) contained in the transport order date of acceptance Format: YYYYMMDD HH:MM DAKOSY-code 4-letter code identifying the participant application usage Alias code. Describes how the participant is identified in another system, e.g. DAK as DAKOSY-code. Other identifiers are not specified yet. participant name just for informal use Password Needs only to be set if required by the specified role. SENDER RECIPIENT EDI_PROVIDER ATLAS number received via ZODIAK HABIS customs number received via HABIS ZOLL operator customer number train number reference number of the actual train location code code of the loading or discharge location automatic processing the customer can a number of automatic processing features for the transport order rcv = automatic receiving fwd = automatic forwarding (requires automatic receiving) qst = automatic retrieval of the quay status (requires a specification of the loading /discharge location) cfd = automatic forwarding depending on a positive quay status (requires automatic receiving and retrieval of the quay status) type of reference used StatusInformation ErrorMessage OrderConfirmation Deletion reference version version of the message / message element ascending sequence (not necassarily continuous) starting with version 01 (new transport order etc) - all versions above 01 are interpreted as a revision of previously communicated data Transaction name StatusInformation Message provider name of the party who is responsible for the underlying scheme. Version of message definition Message type Code defined by the provider for the specified transaction, e.g. GM01 = customs declaration AC03 = StatusInformation TransaktionTyp StatusInformation Transaction information Phone number plain text without validation. Either phone number or e-mail address must be filled if the user-element is transmitted.